From 6664feb693539528c60ecfea83aba9b2f6aac6ca Mon Sep 17 00:00:00 2001 From: Doable8234 Date: Mon, 16 Dec 2024 08:20:44 +0000 Subject: [PATCH] Added a comment --- .../comment_2_8ff41c2d22d49feb7ce8af7feaff7914._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Requesting_of_files_across_disconnected_devices/comment_2_8ff41c2d22d49feb7ce8af7feaff7914._comment diff --git a/doc/forum/Requesting_of_files_across_disconnected_devices/comment_2_8ff41c2d22d49feb7ce8af7feaff7914._comment b/doc/forum/Requesting_of_files_across_disconnected_devices/comment_2_8ff41c2d22d49feb7ce8af7feaff7914._comment new file mode 100644 index 0000000000..8a0f9fd7e0 --- /dev/null +++ b/doc/forum/Requesting_of_files_across_disconnected_devices/comment_2_8ff41c2d22d49feb7ce8af7feaff7914._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Doable8234" + avatar="http://cdn.libravatar.org/avatar/b0d5fea745f92c3b8cc8ecc3dafa6278" + subject="comment 2" + date="2024-12-16T08:20:43Z" + content=""" +I've thought about this exact use case, though I never actually used it yet. One simple way to do this could be by using git annex preferred content settings. In the nodes that push out content, all you need to do is set up a cron job for `git annex sync --content`. Now you can make it push content wherever you want by adjusting the preferred content settings. +"""]] -- 2.30.2